-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add tiup no-sudo doc #20179
add tiup no-sudo doc #20179
Conversation
Hi @Yujie-Xie. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@kaaaaaaang: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
tiup/tiup-cluster-no-sudo-mode.md
Outdated
source ~/.bashrc.d/systemd | ||
``` | ||
|
||
2. Use `root` user to start user service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. Use `root` user to start user service. | |
2. Use the `root` user to start the user service. |
tiup/tiup-cluster-no-sudo-mode.md
Outdated
└─3358 /usr/bin/pulseaudio --daemonize=no --log-target=journal | ||
``` | ||
|
||
Execute `systemctl --user` in the terminal. If no errors are reported, it indicates that it has started normally. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Execute `systemctl --user` in the terminal. If no errors are reported, it indicates that it has started normally. | |
3. Execute `systemctl --user`. If no errors occur, it indicates that the `systemd user` mode has started successfully. |
Co-authored-by: Lilian Lee <[email protected]> Co-authored-by: xixirangrang <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hfxsd The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: base branch (release-8.1) needs to differ from target branch (release-8.1). |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?